Method for carrier selection in vehicle to everything system and terminal device

ABSTRACT

Embodiments of the present disclosure provide a method for carrier selection in a vehicle to everything (V2X) system and a terminal device, including: determining, by a terminal device according to at least one of information of data to be transmitted, information of the terminal device or information of a carrier for current use, whether to perform carrier selection.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/020,816, filed on Sep. 15, 2020, which is a continuation ofInternational Application No. PCT/CN2018/079205, filed on Mar. 15, 2018.The aforementioned patent applications are hereby incorporated byreference in their entireties.

TECHNICAL FIELD

The present disclosure relates to the field of communicationtechnologies and, in particular, to a method for carrier selection in avehicle to everything system (V2X) and a terminal device.

BACKGROUND

A vehicle to everything system is a sidelink (SL) transmissiontechnology based on long term evaluation vehicle to vehicle (LTE V2V).Differing from the traditional LTE system where communication data isreceived or transmitted via a base station, the vehicle to everythingsystem adopts a scheme of terminal-to-terminal direct communication, andtherefore obtaining a higher frequency spectrum efficiency and a lowertransmission delay.

The vehicle to everything (V2X) technology is standardized in version 14(Rel-14) of the 3rd Generation Partnership Project (3GPP), where twotransmission modes are defined: mode 3 and mode 4. Specifically, in mode3, a transmission resource for vehicle user equipment is allocated by abase station, and the vehicle user equipment transmits data on asidelink according to the resource allocated by the base station; thebase station may allocate a resource for a single transmission for theterminal, or may allocate a resource for a semi-static transmission forthe terminal. In mode 4, vehicle user equipment adopts a transmissionscheme of sensing and reservation. Specifically, the vehicle userequipment obtains a set of available transmission resources in aresource pool by way of sensing, and selects a resource randomly fromthe set for data communication.

Currently, the discussion is focused on supporting multi-carriertransmission in the vehicle to everything system, namely, a terminaldevice may concurrently select one or a plurality of carriers frommultiple carriers for data transmission. In such case, with respect to aterminal device, how to trigger the terminal device to perform carrierselection is a problem need to be solved urgently.

SUMMARY

A method for carrier selection in a vehicle to everything system and aterminal device are provided, which can accomplish carrier selection fora terminal device.

A first aspect provides a method for carrier selection in a vehicle toeverything system, including: determining, by a terminal deviceaccording to at least one of information of data to be transmitted,information of the terminal device or information of a carrier forcurrent use, whether to perform carrier selection.

Therefore, in the embodiments of the present disclosure, a terminaldevice may take at least one of the information of the data to betransmitted, the information of the terminal device or the informationof the carrier for current use, as reference information for determiningwhether to trigger the terminal device to perform carrier selection,which is advantageous for satisfying a transmission requirement of thedata to be transmitted, additionally, performing carrier selectionaccording to information of the terminal device is advantageous forimproving a flexibility of resource configuration.

In an implementation, the terminal device may determine, according tothe service type of the data to be transmitted, whether to trigger theterminal device to perform carrier selection. For example, if theservice type of the data to be transmitted is a specific service type,the terminal device may determine to perform carrier selection,otherwise, not to perform carrier selection; or, the terminal device maydetermine, according to the service type of the data to be transmittedand a service type of a service transmitted (i.e. a service alreadytransmitted before a service to be transmitted), whether to performcarrier selection. For example, if the service type of the data to betransmitted and the service type of the service transmitted aredifferent, the terminal device may determine to perform carrierselection, otherwise, determine not to perform carrier selection.

In an implementation, the terminal device may also determine, accordingto the priority information of the data to be transmitted, whether toperform carrier selection. For example, if a priority of the data to betransmitted is higher than a specific priority, the terminal device maydetermine to perform carrier selection, otherwise, determine not toperform carrier selection, where the specific priority may bepre-configured, or configured by a network device.

In an implementation, the terminal device may also determine, accordingto the reliability requirement information of the data to betransmitted, whether to perform carrier selection. For example, if areliability requirement of the data to be transmitted is greater than aspecific reliability threshold (for example, 90%), it is determined toperform carrier selection, where the specific reliability threshold maybe pre-configured, or may also be configured by the network device.

In an implementation, the terminal device may also determine, accordingto the latency information of the data to be transmitted, whether toperform carrier selection. For example, if a latency requirement of thedata to be transmitted is smaller than a specific latency threshold (forexample, 10 ms), it is determined to perform carrier selection, wherethe specific latency threshold may be pre-configured, or may also beconfigured by the network device, which is not limited in theembodiments of the present disclosure.

In an implementation, the terminal device may also determine, accordingto the information of the terminal version supported by the data to betransmitted, whether to perform carrier selection. For example, if theterminal version supported by the data to be transmitted is a specificversion, the terminal device may determine to perform carrier selection,where the specific version may be pre-configured, or configured by thenetwork device.

In a possible implementation manner, the determining, by a terminaldevice according to at least one of information of data to betransmitted, information of the terminal device or information of acarrier for current use, whether to perform carrier selection, includes:

determining, by the terminal device, an available carrier for the datato be transmitted according to the information of the data to betransmitted and a first corresponding relationship; and

determining, by the terminal device according to the available carrierfor the data to be transmitted and the carrier for current use, whetherto perform carrier selection.

In a possible implementation manner, the determining, by the terminaldevice according to the available carrier for the data to be transmittedand the carrier for current use, whether to perform carrier selection,includes:

determining, by the terminal device, to perform carrier selection, ifthe available carrier for the data to be transmitted and the carrier forcurrent use are different.

In a possible implementation manner, the determining, by the terminaldevice according to the available carrier for the data to be transmittedand the carrier for current use, whether to perform carrier selection,includes:

determining, by the terminal device, to perform carrier selection, ifthe available carrier for the data to be transmitted and the carrier forcurrent use are the same, and a reserved resource or a granted resourceon the carrier for current use cannot carry the data to be transmitted.

In a possible implementation manner, the first correspondingrelationship is a corresponding relationship between at least one of aservice type of the data to be transmitted, priority information of thedata to be transmitted, reliability requirement information of the datato be transmitted, latency information of the data to be transmitted orinformation of a terminal version supported by the data to betransmitted, and an available carrier.

In a possible implementation manner, the information of the data to betransmitted includes at least one of the following:

a service type of the data to be transmitted, priority information ofthe data to be transmitted, reliability requirement information of thedata to be transmitted, latency information of the data to betransmitted or information of a terminal version supported by the datato be transmitted.

In a possible implementation manner, the information of the terminaldevice includes a transmission parameter of the terminal device, thedetermining, by a terminal device according to at least one ofinformation of data to be transmitted, information of the terminaldevice or information of a carrier for current use, whether to performcarrier selection, includes:

determining, by the terminal device according to the transmissionparameter of the terminal device, whether to perform carrier selection.

In an implementation, the transmission parameter of the terminal devicemay include at least one of the following:

a modulation and coding scheme (MCS), an available physical resourceblock (PRB), the number of subchannels, the number of retransmissions,or a maximum transmission power.

In a possible implementation manner, the determining, by the terminaldevice according to the transmission parameter of the terminal device,whether to perform carrier selection, includes:

determining, by the terminal device, to perform carrier selection, ifthe transmission parameter of the terminal device changes from a firstavailable parameter range to a second available parameter range, and aparameter within the second available parameter range cannot satisfy atransmission requirement of the data to be transmitted; or determining,by the terminal device, not to perform carrier selection, if thetransmission parameter of the terminal device changes from a firstavailable parameter range to a second available parameter range, and aparameter within the second available parameter range can satisfy atransmission requirement of the data to be transmitted.

In a possible implementation manner, the method further includes:

determining, by the terminal device, a parameter range of thetransmission parameter of the terminal device according to at least oneof a moving speed of the terminal device at present, a synchronizationsource type of the terminal device at present, a channel busy ratio CBRof the terminal device at present, or a priority of the data to betransmitted of the terminal device at present.

In a possible implementation manner, the determining, by the terminaldevice, a parameter range of the transmission parameter of the terminaldevice according to at least one of a moving speed of the terminaldevice at present, a synchronization source type of the terminal deviceat present, a channel busy ratio CBR of the terminal device at present,or a priority of the data to be transmitted of the terminal device atpresent, includes:

determining, by the terminal device, the parameter range of thetransmission parameter of the terminal device according to at least oneof the moving speed of the terminal device at present, thesynchronization source type of the terminal device at present, the CBRof the terminal device at present, or the priority of the data to betransmitted of the terminal device at present, and a secondcorresponding relationship, where the second corresponding relationshipis a corresponding relationship between at least one of a moving speed,a synchronization source type, a channel busy ratio CBR, or a priorityof data, and a parameter range of a transmission parameter.

A second aspect provides a terminal device configured to implement themethod according to the foregoing first aspect or any possibleimplementation manners of the first aspect. Specifically, the terminaldevice includes units configured to execute the method according to theforegoing first aspect or any possible implementation manners of thefirst aspect.

A third aspect provides a terminal device which includes: a memory, aprocessor, an input interface and an output interface. Where the memory,the processor, the input interface and the output interface areinterconnected via a bus system. The memory is configured to storeinstructions, the processor is configured to execute the instructionsstored in the memory to implement the method according to the foregoingfirst aspect or any possible implementation manners of the first aspect.

A fourth aspect provides a computer storage medium which is configuredto store computer software instructions for implementing the methodaccording to the foregoing first aspect or any possible implementationmanners of the first aspect, the instructions includes a programdesigned to implement the foregoing aspects.

A fifth aspect provides a computer program product includinginstructions, which when run on a computer, causes the computer toimplement the method according to the foregoing first aspect or anypossible implementation manners of the first aspect.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic diagram of an application scenario according to anembodiment of the present disclosure;

FIG. 2 is a schematic flowchart of a method for carrier selection in avehicle to everything system according to an embodiment of the presentdisclosure;

FIG. 3 is a schematic diagram of a terminal device according to anembodiment of the present disclosure; and

FIG. 4 is a schematic diagram of a terminal device according to anotherembodiment of the present disclosure.

DESCRIPTION OF EMBODIMENTS

The technical solutions according to the embodiments of the presentdisclosure will be hereinafter described with reference to theaccompanying drawings in the embodiments of the present disclosure.

It should be understood that, the technical solutions of the embodimentsof the present disclosure may be applied to various communicationsystems, such as an LTE system, an LTE frequency division duplex (FDD)system, an LTE time division duplex (TDD) system, a 4.5th Generation(4.5G) network, a 5th Generation (5G) network, new radio (NR) or thelike. The embodiments of the present disclosure may also be applied to avehicle to everything (V2X) system, for example, a vehicle to vehicle(V2V) system; or, may be also applied to a device to device (D2D)system. The embodiments of the present disclosure are not limited to theabove.

It should be understood that, the terminal device in the embodiments ofthe present disclosure may also be referred to as a terminal, a userequipment (UE), a mobile station (MS), a mobile terminal (MT) etc. Theterminal device may be vehicle user equipment (VUE), for example, avehicle or a wireless terminal in self driving and the like; or, theterminal device may also be a pedestrian user equipment (PUE), such as amobile phone, a pad, a computer with a wireless transceiver function orthe like.

It should be understood that, the network device related in theembodiments of the present disclosure is apparatus which is deployed ina wireless access network to provide a wireless communication functionfor a terminal device. The network device may be a base station whichmay include various forms of macro base stations, micro base stations,relay stations, access points or the like. In systems with differentwireless access technologies, a device with a base station function maybe of different names, for example, in an LTE network, it is called anevolved nodeB (eNB or eNodeB), in an 3rd Generation (3G) network, it iscalled an Node B or the like.

FIG. 1 is a schematic diagram of an application scenario according to anembodiment of the present disclosure. As shown in FIG. 1, theembodiments of the present disclosure may be applied in variousapplication scenarios, here, a network device and a terminal device in avehicle to everything system are taken as an example for illustration,where a network device may be a base station 110, a terminal device maybe vehicle user equipment, for example, a vehicle 121 and a vehicle 122.

FIG. 2 is a schematic flowchart of a method 200 for carrier selection ina vehicle to everything system according to an embodiment of the presentdisclosure, the method 200 may be executed by a terminal device in avehicle to everything system, for example, the vehicle user equipment121 or the vehicle user equipment 122 as shown in FIG. 1. As shown inFIG. 2, the method 200 includes:

S210, a terminal device determines, according to at least one ofinformation of data to be transmitted, information of the terminaldevice or information of a carrier for current use, whether to performcarrier selection.

Therefore, in the embodiments of the present disclosure, a terminaldevice may take at least one of information of the data to betransmitted, the information of the terminal device or the informationof the carrier for current use, as reference information for determiningwhether to trigger the terminal device to perform carrier selection,which is advantageous for satisfying a transmission requirement of thedata to be transmitted, additionally, performing carrier selectionaccording to information of the terminal device is advantageous forimproving a flexibility of resource configuration.

It should be understood that the data to be transmitted may include datawhich is newly received and not transmitted yet, or data which isreceived in a recent time period and not transmitted yet, which is notspecifically limited in the embodiments of the present disclosure.

In an implementation, in the embodiments of the present disclosure, theinformation of the carrier for current use may include information ofone carrier, or multiple carriers, which is not limited in theembodiments of the present disclosure.

In an implementation, in the embodiments of the present disclosure, theinformation of the data to be transmitted may include at least one ofthe following:

a service type of the data to be transmitted, priority information ofthe data to be transmitted, reliability requirement information of thedata to be transmitted, latency information of the data to betransmitted or information of a terminal version supported by the datato be transmitted.

As an embodiment, the terminal device may determine, according to theservice type of the data to be transmitted, whether to trigger theterminal device to perform carrier selection. For example, if theservice type of the data to be transmitted is a specific service type,the terminal device may determine to perform carrier selection,otherwise, not to perform carrier selection; or, the terminal device maydetermine, according to the service type of the data to be transmittedand a service type of a service transmitted (i.e. a service alreadytransmitted before a service to be transmitted), whether to performcarrier selection. For example, if the service type of the data to betransmitted and the service type of the service transmitted aredifferent, the terminal device may determine to perform carrierselection, otherwise, determine not to perform carrier selection etc.,the specific condition for triggering the terminal device to performcarrier selection is not limited herein.

As another embodiment, the terminal device may also determine, accordingto the priority information of the data to be transmitted, whether toperform carrier selection. For example, if a priority of the data to betransmitted is higher than a specific priority, the terminal device maydetermine to perform carrier selection, otherwise, determine not toperform carrier selection, where the specific priority may bepre-configured, or configured by a network device.

As still another embodiment, the terminal device may also determine,according to the reliability requirement information of the data to betransmitted, whether to perform carrier selection. For example, if areliability requirement of the data to be transmitted is greater than aspecific reliability threshold (for example, 90%), the terminal devicemay determine to perform carrier selection, where the specificreliability threshold may be pre-configured, or may also be configuredby the network device, which is not limited in the embodiments of thepresent disclosure.

As still another embodiment, the terminal device may also determine,according to the latency information of the data to be transmitted,whether to perform carrier selection. For example, if a latencyrequirement of the data to be transmitted is smaller than a specificlatency threshold (for example, 10 ms), the terminal device maydetermine to perform carrier selection, where the specific latencythreshold may be pre-configured, or may also be configured by thenetwork device, which is not limited in the embodiments of the presentdisclosure.

As still another embodiment, the terminal device may also determine,according to the information of the terminal version supported by thedata to be transmitted, whether to perform carrier selection. Forexample, if the terminal version supported by the data to be transmittedis a specific version, the terminal device may determine to performcarrier selection, where the specific version may be pre-configured, orconfigured by the network device.

In an implementation, the terminal device may also combine two pieces ormore of the above information to determine whether to perform carrierselection. For example, the terminal device may determine, according tothe service type and the priority information of the data to betransmitted, whether to trigger the terminal device to perform carrierselection. For example, when the service type of the data to betransmitted is a specific service type, the terminal device may furthercombine the priority information of the data to be transmitted todetermine whether to perform carrier selection. For example, when apriority of the data to be transmitted is higher than a specificpriority, the terminal device may determine to perform carrierselection, otherwise, not to perform carrier selection.

In an implementation, in some embodiments, the terminal device may alsodetermine, according to information of the data to be transmitted andinformation of the carrier for current use, whether to perform carrierselection.

For example, if a transmission resource on the carrier for current usecannot satisfy a transmission requirement (such as a reliabilityrequirement or a latency requirement etc.) of the data to betransmitted, in such case, the terminal device may determine to performcarrier selection, a step further, the terminal device may select acarrier which can satisfy the transmission requirement of the data to betransmitted as a target carrier to transmit the data; or if thetransmission resource on the carrier for current use can satisfy thetransmission requirement of the data to be transmitted, then theterminal device may determine not to perform carrier selection.

It should be understood that, the above conditions for triggering theterminal device to perform carrier selection are merely exemplary, aspecific condition for triggering the terminal device to perform carrierselection may be adjusted according to information including a specificscenario, a network condition, capacity information of the terminaldevice or the like, which is not specifically limited herein.

It should also be understood that, in the above, the contents includedin the information of the data to be transmitted are merely exemplary,the information of the data to be transmitted may also include otherattribution information of the data to be transmitted, such as Qualityof Service (QoS) information or the like, which is not limited in theembodiments of the present disclosure.

It should be understood that, in the embodiments of the presentdisclosure, the carrier selection may be performed by the terminaldevice in a resource selecting process, or performed separately. Forexample, when a semi-resource of the terminal device expires (or, beinvalidated), the terminal device needs to perform resource selecting,and carrier selection may be performed in a meantime during the resourceselecting process.

In the following, with reference to Embodiment 1, it is specified indetail how a terminal device determines, according to the information ofthe data to be transmitted and the information of the carrier forcurrent use, whether to perform carrier selection.

In Embodiment 1, S210 may specifically include:

determining, by the terminal device, an available carrier for the datato be transmitted according to the information of the data to betransmitted and a first corresponding relationship; and

determining, by the terminal device according to the available carrierfor the data to be transmitted and the carrier for current use, whetherto perform carrier selection.

In an implementation, in Embodiment 1, the first correspondingrelationship is a corresponding relationship between information to betransmitted and available carriers. For example, the first correspondingrelationship may be a corresponding relationship between at least one ofa service type of the data to be transmitted, priority information ofthe data to be transmitted, reliability requirement information of thedata to be transmitted, latency information of the data to betransmitted or information of a terminal version supported by the datato be transmitted, and an available carrier.

In an implementation, the first corresponding relationship may be aone-to-one correspondence, a one-to-many correspondence, or amany-to-one correspondence, or a many-to-many correspondence. Forexample, one service type may correspond to one carrier, or one servicetype may correspond to multiple carriers, or, multiple service typescorrespond to one carrier, or multiple service types correspond tomultiple carriers etc., which is not limited in the embodiments of thepresent disclosure.

Therefore, the terminal device may determine the carrier which the datato be transmitted may use according to the information of the data to betransmitted combined with the first corresponding relationship, a stepfurther, the terminal device may determine, according to the determinedavailable carrier of the data to be transmitted combined with thecarrier for current use, whether to perform carrier selection.

For example, if the carrier for current use and the available carrierwhich is determined according to the first corresponding relationshipare different, in such case, it may be considered that the carrier forcurrent use cannot satisfy the transmission requirement of the data tobe transmitted, or it may be considered that the carrier for current usecannot be used to transmit the data to be transmitted, therefore, theterminal device may determine to perform carrier selection. In apossible implementation manner, the terminal device may select one ormultiple carriers from the available carrier(s) which is(are) determinedaccording to the first corresponding relationship, as a targetcarrier(s) for transmitting the data to be transmitted, so as to satisfythe transmission requirement of the data to be transmitted.

Or, if the carrier for current use and the available carrier which isdetermined according to the first corresponding relationship are thesame, in such case, the terminal device may determine not to performcarrier selection, or further determine whether a reserved resource or agranted resource on the carrier for current use can carry the data to betransmitted, or whether the reserved resource or the granted resource onthe carrier for current use can satisfy the transmission requirement ofthe data to be transmitted, and further determine, according to thedetermination result, whether to perform carrier selection. For example,if the reserved resource or the granted resource on the carrier forcurrent use can carry the data to be transmitted, the terminal devicemay determine not to perform carrier selection, otherwise, determine toperform carrier selection. A step further, the terminal device mayselect one or multiple carriers that can carry the data to betransmitted from the available carrier(s) which is(are) determinedaccording to the first corresponding relationship, as a targetcarrier(s) for transmitting the data to be transmitted.

It is noted that, the carrier for current use and the availablecarrier(s) which is(are) determined according to the first correspondingrelationship being the same may indicate that the carrier for currentuse and the available carrier(s) are partially or completely the same(denoted as Situation 1). For example, the carrier for current use isCarrier 2, the available carriers which are determined according to thefirst corresponding relationship are Carrier 1 and Carrier 2, in suchcase, it may be considered that the carrier for current use and theavailable carriers are the same.

Correspondingly, the carrier for current use and the availablecarrier(s) which is(are) determined according to the first correspondingrelationship being different, may indicate that the carrier for currentuse and the available carrier(s) are completely different (denoted asSituation 2). For example, the carrier for current use is Carrier 3, theavailable carriers which are determined according to the firstcorresponding relationship are Carrier 1 and Carrier 2, in such case, itmay be considered that the carrier for current use and the availablecarriers are different.

An example to illustrate Embodiment 1, if the carrier for current use isCarrier 1, the first corresponding relationship is a correspondingrelationship between service types of data and available carriers, whereService type 1 corresponds to Carrier 1 and Carrier 2, Service type 2corresponds to Carrier 3 and Carrier 4. If a service type of the data tobe transmitted is Service type 1, then the terminal device may determinethat the carrier for current use and the available carriers are the same(corresponding to Situation 1). A step further, the terminal device maydetermine whether a reserved resource or a granted resource on Carrier 1can carry the data to be transmitted, if the data to be transmitted canbe carried, the terminal device may determine not to perform carrierselection, and continue to use a transmission resource on Carrier 1 fordata transmission, or if the data to be transmitted cannot be carried,the terminal device may select a resource which can be used to transmitthe data to be transmitted on Carrier 1 and/or Carrier 2.

One more example, if the carrier for current use is Carrier 1, the firstcorresponding relationship is a corresponding relationship betweenservice types of data and available carriers, where Service type 1corresponds to Carrier 1 and Carrier 2, Service type 2 corresponds toCarrier 3 and Carrier 4. If a service type of the data to be transmittedis Service type 2, then the terminal device may determine that thecarrier for current use and the available carriers are different(corresponding to Situation 2), the terminal device may determine toperform carrier selection. A step further, the terminal device mayselect a resource which can be used to transmit the data to betransmitted on Carrier 3 and/or Carrier 4.

In the following, with reference to Embodiment 2, it is specified indetail how a terminal device determines, according to information of theterminal device, whether to perform carrier selection.

In an implementation, in the embodiments of the present disclosure, theinformation of the terminal device may include a transmission parameterof the terminal device. In an implementation, the transmission parameterof the terminal device may include at least one of the following: amodulation and coding scheme (MCS), an available physical resource block(PRB), the number of subchannels, the number of retransmissions, amaximum transmission power (maxTxPower), where a subchannel may consistof multiple consecutive PRBs, or may include other attributioninformation of the terminal device, such as capability information ofthe terminal device, or a network situation the terminal device ispresently in or the like, which is not limited in the embodiments of thepresent disclosure.

In an implementation, as an embodiment, the terminal device maydetermine, according to whether the transmission parameter of theterminal device changes, whether to perform carrier selection. Forexample, the terminal device may determine to perform carrier selectionwhen the transmission parameter of the terminal device changes,otherwise, determine not to perform carrier selection.

In an implementation, as another embodiment, the terminal device mayalso determine, according to a change amount of the transmissionparameter, whether to perform carrier selection. For example, theterminal device may determine to perform carrier selection when thechange amount of the transmission parameter of the terminal device isgreater than a first threshold, otherwise, determine not to performcarrier selection.

In an implementation, as still another embodiment, the terminal devicemay also determine, according to whether the changed transmissionparameter can satisfy the transmission requirement of the data to betransmitted, whether to perform carrier selection. For example, if thetransmission parameter of the terminal device changes from a firstavailable parameter range to a second available parameter range, and aparameter within the second available parameter range cannot satisfy thetransmission requirement of the data to be transmitted, in such case,the terminal device determines to perform carrier selection, a stepfurther, a carrier which satisfies the transmission requirement of thedata to be transmitted may be selected; or if the transmission parameterof the terminal device changes from the first available parameter rangeto the second available parameter range, and a parameter within thesecond available parameter range can satisfy the transmissionrequirement of the data to be transmitted, the terminal device maydetermine not to perform carrier selection.

In an implementation, in some embodiments, the method 200 may furtherinclude:

determining, by the terminal device, a parameter range of thetransmission parameter of the terminal device according to at least oneof a moving speed of the terminal device at present, a synchronizationsource type of the terminal device at present, a channel busy ratio CBRof the terminal device at present, or a priority of the data to betransmitted of the terminal device at present.

Where, the channel busy ratio (CBR) may be used to indicate a congestionlevel of a network, the synchronization source type includes but is notlimited to a Global Navigation Satellite System (GNSS), an eNB and a UE.

In an implementation, in some embodiments, at least one of a movingspeed of the terminal device at present, a synchronization source typeof the terminal device at present, a channel busy ratio CBR of theterminal device at present, or a priority of the data to be transmittedof the terminal device at present, and a parameter range of atransmission parameter may have a second corresponding relationship,where the second relationship may be pre-configured by a network device,or may be pre-configured on the terminal device.

In an implementation, the second corresponding relationship may be aone-to-one correspondence, a one-to-many correspondence, or amany-to-one correspondence, or a many-to-many correspondence. Forexample, one synchronization source type may correspond to one group oftransmission parameters, or multiple synchronization source types maycorrespond to one group of transmission parameters, or one speed rangeand one synchronization source type correspond to one group oftransmission parameters etc., which is not limited in the embodiments ofthe present disclosure.

As an example rather than limitation, the second correspondingrelationship may be shown in table 1:

TABLE 1 Speed range ≤120 km/h >120 km/h Synchronization GNSS MCS [0, 28][0, 10] source types PRB number [1, 50] [1, 16] The number of {0, 1} 1retransmissions Maximum 23 dBm 23 dBm transmission (decibel milliwatt)power eNB MCS [0, 21] [0, 6] PRB number [1, 30] [1, 8] The number of {0,1} 1 retransmissions Maximum 23 dBm 23 dBm transmission power UE MCS [0,9] [0, 4] PRB number [1, 10] [1, 4] The number of {0, 1} 1retransmissions Maximum 23 dBm 23 dBm transmission power

For example, if the present synchronization source type is GNSS, when aspeed of the terminal device changes from being smaller than 120 km/h tobeing greater than 120 km/h, the terminal device may determine,according to the corresponding relationship as shown in table 1, anavailable PRB number range changes from [1,50] to [1,16]. If an PRBnumber required for the data to be transmitted is greater than 16, insuch case, the terminal device may determine that the changed availableparameter range cannot satisfy a transmission requirement of the data tobe transmitted, thus the terminal device may be triggered to performcarrier selection, or, the terminal device may be triggered to performresource selection, specifically, carrier selection may be performedduring a resource selecting process.

In an implementation, in some embodiments, the data to be transmittedmay be first data newly received, therefore, the terminal device mayalso determine, according to a service type and/or attributioninformation of the first data, whether to perform carrier selection.

In the following, with reference to Embodiment 3 to Embodiment 7, amethod for carrier selection according to another embodiment isspecified in detail.

Embodiment 3: performing carrier selection according to a service typeof first data.

In an exemplary embodiment of Embodiment 3, the terminal device maydetermine, according to the service type of the first data and a servicetype of second data, whether to perform carrier selection, where areceived time of the second data is earlier than a received time of thefirst data.

Namely, the terminal device may determine, according to a service typeof a service newly received (i.e. the first data) and a service type ofan existing service (i.e. the second data), whether to perform carrierselection. Where the second data may refer to service data receivedbefore the first data and not yet transmitted.

In an implementation, as an embodiment, the terminal device maydetermine to perform carrier selection when the service type of thefirst data and the service type of the second data are different. Or,when the service type of the first data and the service type of thesecond data are different, the terminal device may further combineattribution information of the first data, for example, priorityinformation, latency information or the like, to determine whether toperform carrier selection, reference may be made to the relateddescription in Embodiment 4 to Embodiment 7 for the specificimplementation thereof.

In an implementation, as another embodiment, if the service type of thefirst data and the service type of the second data are the same, theterminal device may determine not to perform carrier selection, or theterminal device may further combine the attribution information of thefirst data (for example, the priority information, the latencyinformation or the like), to determine whether to perform carrierselection, reference may be made to the related description inEmbodiment 4 to Embodiment 7 for the specific implementation thereof.

In an implementation, as still another embodiment, the terminal devicemay determine to perform carrier selection when the service type of thefirst data newly received is a specific service type, where the specificservice type may be pre-configured, or may be configured by a networkdevice.

In an implementation, as still another embodiment, the terminal devicemay determine, according to the service type of the first data and atransmitting capacity of the terminal device, whether to perform carrierselection. For example, if the transmitting capacity of the terminaldevice is not restrained, the terminal device may determine to performcarrier selection when the first data is received. Or, if thetransmitting capacity of the terminal device is restrained, the terminaldevice may determine not to perform carrier selection, or may furthercombine attribution information of the first data to determine whetherto perform carrier selection. For example, if a priority of the firstdata is higher than a priority of the second data, then the terminaldevice may determine to perform carrier selection for the first datapreferentially, that is, to select a transmission resource for the firstdata preferentially; or, if the priority of the first data is lower thanthe priority of the second data, then the terminal device may determinenot to perform carrier selection.

When the terminal device determines to perform carrier selection for thefirst data, a step further, the terminal device may determine for thefirst data, according to the service type of the first data and theforegoing first corresponding relationship, a target carrier selected.

For example, if the service type of the first data is a cooperateawareness message (CAM), the service type of the second data is adecentralized environmental notification message (DENM). On receivingthe first data, the terminal device may determine the service type ofthe first data and that of the second data are different, then triggerthe terminal device to perform carrier selection.

Situation 1: the service type of the first data and the service type ofthe second data correspond to different carriers, for example, in thefirst corresponding relationship, CAM corresponds to Carrier 1 andCarrier 2, DENM corresponds to Carrier 3 and Carrier 4, then theterminal device may select a transmission resource for the first data onCarrier 3 or Carrier 4.

Situation 2: the service type of the first data and the service type ofthe second data correspond to the same carrier, for example, in thefirst corresponding relationship, CAM corresponds to Carrier 1 andCarrier 2, DENM also corresponds to Carrier 1 and Carrier 2, if thetransmission resource presently used by the terminal device is onCarrier 2, then the terminal device may select a transmission resourcefor the first data on Carrier 1 or Carrier 2.

Embodiment 4: the attribution information of the first data is thepriority information, the terminal device performs carrier selectionaccording to the priority information of the first data.

For example, when a priority of the first data is higher than a specificpriority, the terminal device may determine to perform carrierselection, where, the specific priority may be pre-configured, or may beconfigured by a network device.

In an implementation, as an embodiment, the terminal device maydetermine, according to the priority information of the first data andpriority information of second data, whether to perform carrierselection, where a received time of the second data is earlier than areceived time of the first data.

It should be understood that, in Embodiment 4, a service type of thefirst data and the second data may be the same, or different, which isnot limited in the embodiment of the present disclosure.

Situation 1: if the service type of the first data and the second dataare the same, then priorities of the first data and the second data maybe determined according to a ProSe Per-Packet Priority (PPPP) of anadjacent service. For example, if the first data and the second data areboth CAM, the PPPP of the first data is 1, the PPPP of the second datais 4, then it may be determined that the priority of the first data ishigher than the priority of the second data.

Situation 2: if the service type of the first data and the second dataare different, the priorities of the first data and the second data maybe determined according to the corresponding PPPPs. For example, ifPPPP=4 for the service type CAM is considered as being equal to PPPP=4for DENM, then if the service type of the first data is CAM, PPPP=3, theservice type of the second data is DENM, PPPP=3, then it may bedetermined that the priority of the second data is higher than thepriority of the first data.

In a specific embodiment of Embodiment 4, the determining, by theterminal device, according to the priority information of the first dataand the priority information of the second data, whether to performcarrier selection includes:

determining, by the terminal device, to perform carrier selection if thepriority of the first data is higher than the priority of the seconddata.

Specifically, if the priority of the first data is higher than thepriority of the second data, the terminal device may determine toperform carrier selection for the first data preferentially. In apossible implementation manner, the terminal device may determine forthe first data, according to the priority of the first data and theforegoing first corresponding relationship, a target carrier selected.

In an implementation, in the embodiments of the present disclosure, ifthe priority of the first data is lower than the priority of the seconddata, the terminal device may determine not to perform carrierselection, or, in such case, the terminal device may further combine atransmitting capacity of the terminal device or other attributioninformation, to determine whether to perform carrier selection. Forexample, if the transmitting capacity of the terminal device is notrestrained, the terminal device may determine to perform carrierselection, the terminal device selects a carrier for transmitting thefirst data from the available carrier(s) corresponding to the priorityof the first data, without changing a carrier for transmitting thesecond data, reference may be made to the related description in theforegoing embodiments for the specific implementation of the carrierselection, or, if the transmitting capacity of the terminal device isrestrained, the terminal device may determine not to perform carrierselection.

Embodiment 5: the attribution information of the first data isreliability requirement information, the terminal device determines,according to the reliability requirement information of the first data,whether to perform carrier selection.

In an implementation, the terminal device may determine to performcarrier selection when a reliability requirement of the first data isgreater than a specific reliability threshold (for example, 90%), wherethe specific reliability threshold may be pre-configured, or may beconfigured by a network device, which is not limited in the embodimentof the present disclosure.

In an implementation, as an embodiment, the terminal device maydetermine, according to the reliability requirement information of thefirst data and reliability requirement information of the second data,whether to perform carrier selection, where a received time of thesecond data is earlier than a received time of the first data.

For example, if the reliability requirement of the first data (forexample, 90%) is higher than a reliability requirement of the seconddata (for example, 80%), the terminal device determines to performcarrier selection. Or if the reliability requirement of the first datais lower than the reliability requirement of the second data, theterminal device may determine not to perform carrier selection, or, insuch case, the terminal device may further combine a transmittingcapacity of the terminal device or other attribution information, todetermine whether to perform carrier selection. For example, if thetransmitting capacity of the terminal device is not restrained, theterminal device may determine to perform carrier selection, referencemay be made to the related description in the foregoing embodiments forthe specific implementation of the carrier selection, or, if thetransmitting capacity of the terminal device is restrained, the terminaldevice may determine not to perform carrier selection.

When the terminal device determines to perform carrier selection, theterminal device may determine to perform carrier selection for the firstdata preferentially. In a possible implementation manner, the terminaldevice may determine for the first data, according to the reliabilityrequirement of the first data and the foregoing first correspondingrelationship, a target carrier selected.

Embodiment 6: the attribution information of the first data is latencyinformation, the terminal device determines whether to perform carrierselection according to the latency information of the first data.

In an implementation, the terminal device may determine to performcarrier selection when a latency requirement of the first data issmaller than a specific latency threshold (for example, 10 ms), wherethe specific latency threshold may be pre-configured, or may beconfigured by a network device, which is not limited in the embodimentof the present disclosure.

In an implementation, as an embodiment, the terminal device maydetermine, according to the latency information of the first data andlatency information of second data, whether to perform carrierselection, where a received time of the second data is earlier than areceived time of the first data.

For example, if the latency requirement of the first data (for example,5 ms) is smaller than a latency requirement of the second data (forexample, 10 ms), the terminal device determines to perform carrierselection. Or if the latency requirement of the first data is greaterthan the latency requirement of the second data, the terminal device maydetermine not to perform carrier selection, or, in such case, theterminal device may further combine a transmitting capacity of theterminal device or other attribution information, to determine whetherto perform carrier selection. For example, if the transmitting capacityof the terminal device is not restrained, the terminal device maydetermine to perform carrier selection, reference may be made to therelated description in the foregoing embodiments for the specificimplementation of the carrier selection, or, if the transmittingcapacity of the terminal device is restrained, the terminal device maydetermine not to perform carrier selection.

When the terminal device determines to perform carrier selection, theterminal device may determine to perform carrier selection for the firstdata preferentially. In a possible implementation manner, the terminaldevice may determine for the first data, according to the latencyrequirement of the first data and the foregoing first correspondingrelationship, a target carrier selected.

Embodiment 7: the attribution information of the first data isinformation of a terminal version supported by the first data, theterminal device performs carrier selection according to the informationof the terminal version supported by the first data.

For example, the terminal device may determine to perform carrierselection when a terminal supported by the first data is of a specificversion, where the specific version may be pre-configured, or may beconfigured by a network device.

In an implementation, as an embodiment, the terminal device maydetermine, according to the information of the terminal versionsupported by the first data and information of the terminal versionsupported by second data, whether to perform carrier selection, where areceived time of the second data is earlier than a received time of thefirst data.

For example, if a terminal version supported by the first data is lowerthan a terminal version supported by the second data, the terminaldevice determines to perform carrier selection.

Specifically, when the terminal version supported by the first data islower than the terminal version supported by the second data, theterminal device may determine to perform carrier selection for the firstdata preferentially. In a possible implementation manner, the terminaldevice may determine for the first data, according to the information ofthe terminal version supported by the first data and the foregoing firstcorresponding relationship, a target carrier selected.

In an implementation, in the embodiment, if the terminal versionsupported by the first data is lower than the terminal version supportedby the second data, the terminal device may determine not to performcarrier selection, or, in such case, the terminal device may furthercombine a transmitting capacity of the terminal device or otherattribution information, to determine whether to perform carrierselection. For example, if the transmitting capacity of the terminaldevice is not restrained, the terminal device may determine to performcarrier selection, reference may be made to the related description inthe foregoing embodiments for the specific implementation of the carrierselection, or, if the transmitting capacity of the terminal device isrestrained, the terminal device may determine not to perform carrierselection.

In the above, with reference to Embodiment 3 to Embodiment 7, it isspecified in detail how it is determined, according to the service typeand/or the attribution information of the first data, whether to performcarrier selection. It should be understood that, the above Embodiment 3to Embodiment 7 may be used separately or in combination, which is notlimited in the embodiments of the present disclosure.

The method embodiments of the present disclosure are specified in detailin the above with reference to FIG. 2, and the device embodiments of thepresent disclosure will be specified in detail in the following withreference to FIG. 3 and FIG. 4.

FIG. 3 is a schematic diagram of a terminal device 300 according to anembodiment of the present disclosure. As shown in FIG. 3, the terminaldevice 300 includes:

a determining module 310, configured to determine, according to at leastone of information of data to be transmitted, information of theterminal device or information of a carrier for current use, whether toperform carrier selection.

In an implementation, in some embodiments, the determining module 310 isspecifically configured to:

determine an available carrier for the data to be transmitted accordingto the information of the data to be transmitted and a firstcorresponding relationship; and

determine, according to the available carrier for the data to betransmitted and the carrier for current use, whether to perform carrierselection.

In an implementation, in some embodiments, the determining module 310 isspecifically configured to:

determine to perform carrier selection, if the available carrier for thedata to be transmitted and the carrier for current use are different.

In an implementation, in some embodiments, the determining module 310 isfurther configured to:

determine to perform carrier selection, if the available carrier for thedata to be transmitted and the carrier for current use are the same, anda reserved resource or a granted resource on the carrier for current usecannot carry the data to be transmitted.

In an implementation, in some embodiments, the first correspondingrelationship is a corresponding relationship between at least one of aservice type of the data to be transmitted, priority information of thedata to be transmitted, reliability requirement information of the datato be transmitted, latency information of the data to be transmitted orinformation of a terminal version supported by the data to betransmitted, and an available carrier.

In an implementation, in some embodiments, the information of the datato be transmitted includes at least one of the following:

a service type of the data to be transmitted, priority information ofthe data to be transmitted, reliability requirement information of thedata to be transmitted, latency information of the data to betransmitted or information of a terminal version supported by the datato be transmitted.

In an implementation, in some embodiments, the information of theterminal device includes a transmission parameter of the terminaldevice, the determining module 310 is further configured to:

determine whether to perform carrier selection according to thetransmission parameter of the terminal device.

In an implementation, in some embodiments, the determining module 310 isspecifically configured to:

determine to perform carrier selection, if the transmission parameter ofthe terminal device changes from a first available parameter range to asecond available parameter range, and a parameter within the secondavailable parameter range cannot satisfy a transmission requirement ofthe data to be transmitted; or

determine not to perform carrier selection, if the transmissionparameter of the terminal device changes from a first availableparameter range to a second available parameter range, and a parameterwithin the second available parameter range can satisfy a transmissionrequirement of the data to be transmitted.

In an implementation, in some embodiments, the determining module 310 isfurther configured to:

determine a parameter range of the transmission parameter of theterminal device according to at least one of a moving speed of theterminal device at present, a synchronization source type of theterminal device at present, a channel busy ratio CBR of the terminaldevice at present, or a priority of the data to be transmitted of theterminal device at present.

In an implementation, in some embodiments, the determining module 310 isspecifically configured to:

determine the parameter range of the transmission parameter of theterminal device, according to at least one of the moving speed of theterminal device at present, the synchronization source type of theterminal device at present, the CBR of the terminal device at present,or the priority of the data to be transmitted of the terminal device atpresent, and a second corresponding relationship, wherein the secondcorresponding relationship is a corresponding relationship between atleast one of a moving speed, a synchronization source type, a channelbusy ratio CBR, or a priority of data, and a parameter range of atransmission parameter.

It should be understood that, the terminal device 300 according to theembodiments of the present disclosure may correspond to the terminaldevice in the method embodiments of the present disclosure, and theforegoing and other operations and/or functions of the various units ofthe terminal device 300 are respectively designed to implement thecorresponding procedure of the terminal device according to the method200 as shown in FIG. 2, which will not be repeated here for conciseness.

As shown in FIG. 4, a terminal device 400 is provided in the embodimentof the present disclosure, the terminal device 400 may be the terminaldevice 300 as shown in FIG. 3, which can be configured to perform thecontent corresponding to the terminal device in the method 200 as shownin FIG. 2. The terminal device 400 includes: an input interface 410, anoutput interface 420, a processor 430 and a memory 440, the inputinterface 410, the output interface 420, the processor 430 and thememory 440 may be interconnected via a bus system. The memory 440 isconfigured to store programs, instructions or codes. The processor 430is configured to execute the programs, instructions or codes stored inthe memory 440, to control the input interface 410 to receive signalsand control the output interface 420 to transmit signals, so as toimplement operations according to the foregoing method embodiments.

It should be understood, in the embodiments of the present disclosure,the processor 430 may be a central processing unit (CPU), and theprocessor 430 may also be a general-purpose processor or a digitalsignal processor (DSP), an application-specific integrated circuit(ASIC), a ready-made programmable gate array (FPGA) or otherprogrammable logic device, a discrete gate or transistor logic device, adiscrete hardware component or the like. The general-purpose processormay be a microprocessor or the processor may also be any conventionalprocessors or the like.

The memory 440 may include a read-only memory and a random accessmemory, and provides instructions and data to the processor 430. A partof the memory 440 may also include a non-volatile random access memory.For example, the memory 440 may also store information of a device type.

In the process of implementing, the content in the foregoing method maybe implemented by a hardware integrated logic circuit in the processor430 or instructions in the form of software. The contents of the methoddisclosed in the embodiments of the present disclosure in combination,may be directly embodied as being executed by a hardware processor, orexecuted by a combination of hardware and software modules in theprocessor. The software modules can be located in a storage medium whichis mature in the present field such as a random access memory, a flashmemory, a read-only memory, a programmable read-only memory, anelectrically erasable programmable memory or a register. The storagemedium is located in the memory 440, and the processor 430 readsinformation in the memory 440 to implement, in combination with itshardware, the content of the foregoing method, which will not bedescribed in detail herein for the sake of brevity.

In a specific implementation, the determining module 310 included in theterminal device 300 as shown in FIG. 3 may be implemented by theprocessor 430 in FIG. 4.

An embodiment of the present disclosure also proposes a computerreadable storage medium which is configured to store one or multipleprograms including instructions, which when being executed by a portableelectronic device including multiple applications, cause the portableelectronic device to implement the method according to the embodiment asshown in FIG. 2.

An embodiment of the present disclosure also proposes a computer programincluding instructions, which when run on a computer, causes thecomputer to implement the corresponding procedure of the methodaccording to the embodiment as shown in FIG. 2.

A person ordinary skilled in the art may realize, the various exemplaryunits and algorithm steps disclosed herein in combination, can beimplemented by an electronic hardware, or a combination of computersoftware and an electronic hardware. Whether these functions areimplemented by a hardware or a software depends on a specificapplication and a design constraint condition of the technical solution.Professional and technical personnel can use different methods toimplement the functions described with respect to each specificapplication, however, such implementation should not be considered asgoing beyond the scope of the present disclosure.

A person skilled in the art can clearly understand that, for theconvenience and conciseness of description, reference may be made to thecorresponding process in the foregoing method embodiments for thespecific working process of the system, device and unit described above,which will not be repeated herein again.

In the several embodiments provided in the present disclosure, it shouldbe understood that the disclosed system, device, and method can beimplemented in other manners. For example, the device embodimentsdescribed above are merely illustrative. For example, the dividing ofthe units is only a logical function division, and there may be otherdivision manners in a practical implementation. For example, multipleunits or components may be combined with or integrated into anothersystem, or some features may be omitted or not executed. In addition,the mutual coupling or direct coupling or communication connection shownor discussed may be an indirect coupling or a communication connectionthrough some interfaces, devices or units, which may be electrical,mechanical or otherwise.

The units described as discrete components may or may not be physicallyseparated, a component shown as a unit may or may not be a physicalunit, namely, it may be located in one place, or may be distributed inmultiple network elements. Some or all of the units may be selectedaccording to practical needs to achieve the purpose of the solution ofthe embodiments.

In addition, the various function units in each embodiment of thepresent disclosure may be integrated in one processing unit, or eachunit may physically exist alone, or two or more units may be integratedin one unit.

The functions may be stored in a computer readable storage medium ifbeing implemented in the form of a software function unit and sold orused as a stand-alone product. Based on such understanding, thetechnical solutions of the present disclosure, substantively, or a partof which that makes a contribution to the prior art, or a part of which,may be embodied in the form of a software product, the computer softwareproduct is stored in a storage medium and includes several instructionsto cause a computer (which may be a personal computer, a server, anetwork device or the like) to execute all or part of the steps of themethods described in the various embodiments of the present disclosure.The foregoing storage medium includes: a USB flash disk, a mobile harddisk drive, a read-only memory (ROM), a random access memory (RAM), amagnetic disk or an optical disk, or other medium that can store programcodes.

The foregoing description is simply specific embodiments of the presentdisclosure, however, the protection scope of the present disclosure isnot limited thereto. Any alteration or substitution that a personskilled in the art may easily acquire within the technical scopedisclosed by the present disclosure, shall all be encompassed in theprotection scope of the present disclosure. Therefore, the protectionscope of the present disclosure shall be subject to the protection scopeof the claims.

What is claimed is:
 1. A method for carrier selection, comprising:acquiring, by a terminal device, information of data to be transmitted;acquiring, by the terminal device, information of a carrier configuredfor use; determining, by the terminal device, an available carrier forthe data to be transmitted according to the information of the data tobe transmitted and a first corresponding relationship; and triggering,by the terminal device, carrier selection at least based on theavailable carrier for the data to be transmitted and the carrierconfigured for use.
 2. The method according to claim 1, wherein thetriggering, by the terminal device, carrier selection at least based onthe available carrier for the data to be transmitted and the carrierconfigured for use, comprises: triggering, by the terminal device,carrier selection, if the available carrier for the data to betransmitted and the carrier configured for use are different.
 3. Themethod according to claim 1, wherein the triggering, by the terminaldevice, carrier selection at least based on the available carrier forthe data to be transmitted and the carrier configured for use,comprises: triggering, by the terminal device, carrier selection, if theavailable carrier for the data to be transmitted and the carrierconfigured for use are the same, and no reserved resource or grantedresource on the carrier configured for use is allowed to carry the datato be transmitted.
 4. The method according to claim 1, wherein thetriggering, by the terminal device, carrier selection at least based onthe available carrier for the data to be transmitted and the carrierconfigured for use, comprises: triggering, by the terminal device,carrier selection based on the available carrier for the data to betransmitted, the carrier configured for use and a transmission parameterof the terminal device.
 5. The method according to claim 1, wherein theinformation of the data to be transmitted comprises at least one of thefollowing: a service type of the data to be transmitted, priorityinformation of the data to be transmitted, reliability requirementinformation of the data to be transmitted, latency information of thedata to be transmitted or information of a terminal version supported bythe data to be transmitted.
 6. The method according to claim 1, whereinthe first corresponding relationship is a corresponding relationshipbetween an available carrier and at least one of: a service type of thedata to be transmitted, priority information of the data to betransmitted, reliability requirement information of the data to betransmitted, latency information of the data to be transmitted orinformation of a terminal version supported by the data to betransmitted.
 7. The method according to claim 4, wherein the triggering,by the terminal device, carrier selection based on the available carrierfor the data to be transmitted, the carrier configured for use and atransmission parameter of the terminal device, comprises: triggering, bythe terminal device, carrier selection, if the transmission parameter ofthe terminal device is within a parameter range which cannot satisfy atransmission requirement of the data to be transmitted.
 8. The methodaccording to claim 7, further comprising: determining, by the terminaldevice, a parameter range of the transmission parameter of the terminaldevice according to at least one of a moving speed of the terminaldevice, a synchronization source type of the terminal device, a channelbusy ratio (CBR) of the terminal device, or a priority of data to betransmitted of the terminal device.
 9. The method according to claim 8,wherein the determining, by the terminal device, a parameter range ofthe transmission parameter of the terminal device according to at leastone of a moving speed of the terminal device, a synchronization sourcetype of the terminal device, a channel busy ratio (CBR) of the terminaldevice, or a priority of the data to be transmitted of the terminaldevice, comprises: determining, by the terminal device, the parameterrange of the transmission parameter of the terminal device according toat least one of the moving speed of the terminal device at present, thesynchronization source type of the terminal device at present, the CBRof the terminal device at present, or the priority of the data to betransmitted of the terminal device at present, and a secondcorresponding relationship, wherein the second correspondingrelationship is a corresponding relationship between at least one of amoving speed, a synchronization source type, a CBR, or a priority ofdata, and a parameter range of a transmission parameter.
 10. A terminaldevice, comprising: a memory, a processor, an input interface and anoutput interface, wherein the memory, the processor, the input interfaceand the output interface are interconnected via a bus system, the memoryis configured to store instructions, the processor is configured to:acquire information of data to be transmitted; acquire information of acarrier configured for use; determine an available carrier for the datato be transmitted according to the information of the data to betransmitted and a first corresponding relationship; and trigger carrierselection at least based on the available carrier for the data to betransmitted and the carrier configured for use.
 11. The terminal deviceaccording to claim 10, wherein the processor is configured to: triggercarrier selection, if the available carrier for the data to betransmitted and the carrier configured for use are different.
 12. Theterminal device according to claim 10, wherein the processor isconfigured to: trigger carrier selection, if the available carrier forthe data to be transmitted and the carrier configured for use are thesame, and no reserved resource or granted resource on the carrierconfigured for use is allowed to carry the data to be transmitted. 13.The terminal device according to claim 10, wherein the processor isconfigured to: trigger carrier selection based on the available carrierfor the data to be transmitted, the carrier configured for use and atransmission parameter of the terminal device.
 14. The terminal deviceaccording to claim 10, wherein the information of the data to betransmitted comprises at least one of the following: a service type ofthe data to be transmitted, priority information of the data to betransmitted, reliability requirement information of the data to betransmitted, latency information of the data to be transmitted orinformation of a terminal version supported by the data to betransmitted.
 15. The terminal device according to claim 10, wherein thefirst corresponding relationship is a corresponding relationship betweenan available carrier and at least one of: a service type of the data tobe transmitted, priority information of the data to be transmitted,reliability requirement information of the data to be transmitted,latency information of the data to be transmitted or information of aterminal version supported by the data to be transmitted.
 16. Theterminal device according to claim 13, wherein the processor isconfigured to: trigger carrier selection, if the transmission parameterof the terminal device is within a parameter range which cannot satisfya transmission requirement of the data to be transmitted.
 17. Theterminal device according to claim 16, wherein the processor is furtherconfigured to: determine a parameter range of the transmission parameterof the terminal device according to at least one of a moving speed ofthe terminal device, a synchronization source type of the terminaldevice, a channel busy ratio (CBR) of the terminal device, or a priorityof data to be transmitted of the terminal device.
 18. The terminaldevice according to claim 17, wherein the processor is configured to:determine the parameter range of the transmission parameter of theterminal device according to at least one of the moving speed of theterminal device at present, the synchronization source type of theterminal device at present, the CBR of the terminal device at present,or the priority of the data to be transmitted of the terminal device atpresent, and a second corresponding relationship, wherein the secondcorresponding relationship is a corresponding relationship between atleast one of a moving speed, a synchronization source type, a CBR, or apriority of data, and a parameter range of a transmission parameter. 19.A computer-readable storage medium, storing thereon computer executableinstructions which, when being executed by a processor, implement themethod for carrier selection according to claim 1.